Let's say there is a module whose full path is given by the string variable modname. Let's also say that I can open and view this module in DOORS without any obvious problem. Now, let's suppose, I run a very simple snippet of code:
What are the possible reasons that would explain an output of 'null'? This has been baffling me for weeks now. Thanks, Grasswistle grasswistle - Tue Nov 19 13:53:45 EST 2013 |
Re: What does the null module message mean You should add a second parameter to the read() function.
Module m = read(string modname, bool display) Also carefully check the spelling of your module name and ensure you are using the full path to the parent project with preceeding slash. |
Re: What does the null module message mean Tony_Goodman - Wed Nov 20 06:48:18 EST 2013 You should add a second parameter to the read() function.
Module m = read(string modname, bool display) Also carefully check the spelling of your module name and ensure you are using the full path to the parent project with preceeding slash. According to DXL manual, you should not need the second parameter. If it is omitted, the module should be visible when opened. Does it open up? Tony is right to check the spelling of the module name. A missing "/" at the beginning of the path will cause a null. Should be "/project/folder/module name" Hope this helps, Greg |
Re: What does the null module message mean GregM_dxler - Wed Nov 20 09:04:16 EST 2013 According to DXL manual, you should not need the second parameter. If it is omitted, the module should be visible when opened. Does it open up? Tony is right to check the spelling of the module name. A missing "/" at the beginning of the path will cause a null. Should be "/project/folder/module name" Hope this helps, Greg
Thanks for your input so far.
Here is some extra information:
Any other ideas--even theories?
Grasswistle
|
Re: What does the null module message mean grasswistle - Wed Nov 20 13:17:16 EST 2013
Thanks for your input so far.
Here is some extra information:
Any other ideas--even theories?
Grasswistle
Don't know for sure. Nothing sticks in my head as to that dxl command changing over the past few versions, but I'm not as learned as others in the forum. Is the problem with only a single module or is it with the dxl command? Did you check to see if the module is already opened in another mode? Even in the background? I would have to assume that since you can open the module, then there is no problems with access rights. What about views? Has the views changed in the module? Maybe try loading the standard view to see if it helps. Greg |
Re: What does the null module message mean Not sure how you are getting the value for modname variable, but if it isn't through the code itself, then there's a good chance that the string is incorrect, leading to the problem. Maybe the module name has an extra blank space at the end? Select the module in question on right-pane of DOORS Explorer and run the following line (I'm printing the value enclosed in double-quotes so that it'll show if there's an additional blank space at the end): print "\"" fullName(getSelectedItem) "\""
If this does not throw an error, try passing this string into the read perm - I would expect it to work.. If the above line throw null item error, I'd suggest you to contact support.. we can have it investigated formally. |
Re: What does the null module message mean SudarshanRao - Thu Nov 21 03:08:00 EST 2013 Not sure how you are getting the value for modname variable, but if it isn't through the code itself, then there's a good chance that the string is incorrect, leading to the problem. Maybe the module name has an extra blank space at the end? Select the module in question on right-pane of DOORS Explorer and run the following line (I'm printing the value enclosed in double-quotes so that it'll show if there's an additional blank space at the end): print "\"" fullName(getSelectedItem) "\""
If this does not throw an error, try passing this string into the read perm - I would expect it to work.. If the above line throw null item error, I'd suggest you to contact support.. we can have it investigated formally. You're right, there was the slightest difference in the strings. Ugh. Sorry to waste your time with this. Thanks, Grasswistle |